chore(deps): update dependency jsdom to v27.4.0 - #200
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
November 2, 2025 11:36
50caefe to
067644f
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
November 10, 2025 16:44
067644f to
483c6e9
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
November 16, 2025 23:54
483c6e9 to
b3437aa
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
December 3, 2025 17:04
b3437aa to
c4397a9
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
December 8, 2025 15:12
c4397a9 to
a3388b4
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
December 26, 2025 12:05
a3388b4 to
7c96dda
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
2 times, most recently
from
January 9, 2026 15:15
a42f997 to
4452bdd
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
January 20, 2026 11:45
4452bdd to
41db1e0
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
February 2, 2026 20:15
41db1e0 to
333948d
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
February 14, 2026 03:06
333948d to
0e7a64f
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
March 8, 2026 09:14
0e7a64f to
6e10cff
Compare
renovate
Bot
force-pushed
the
renovate/jsdom-27.x
branch
from
May 13, 2026 23:30
6e10cff to
c54fd25
Compare
Contributor
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
27.0.0→27.4.0Release Notes
jsdom/jsdom (jsdom)
v27.4.0Compare Source
TextEncoderandTextDecoder.@exodus/bytespackage; it is now much more correct. (@ChALkeR)<meta charset>or using the parent frame's encoding.Ranges were used and then the elements referred to by those ranges were removed.v27.3.0Compare Source
@acemir/cssom. (@acemir)v27.2.0Compare Source
CSSGroupingRule,CSSNestedDeclarations,CSSConditionRule,CSSContainerRule,CSSScopeRule,CSSSupportsRule,CSSLayerBlockRule, andCSSLayerStatementRuleto jsdomWindows. (@acemir)@acemir/cssom. (@acemir)@import-ed stylesheets to be properly exposed to CSSOM, and not to overwrite the sheet created from the<link>or<style>element. (@acemir)v27.1.0Compare Source
@acemir/cssom, including support for nested selectors, nested declarations, layer statements, and improved at-rule validation. (@acemir)package.json"engines"field to reflect the new minimum Node.js versions needed to run jsdom, as noted in the changelog for v27.0.1.v27.0.1Compare Source
This release inadvertently raised the minimum Node.js version from v20.0.0 to v20.19.0+, v22.12.0+, v24.0.0+. (This happened via a dependency update.) This probably should have been a breaking (major) change, instead of happening in a patch version, since it prevents using earlier Node.js versions.
After further testing, we found that most of our development dependencies also require these versions, and so it's not feasible for the jsdom project to support earlier Node.js versions. (For example, our testing frameworks will not run on them.) If you need to use such earlier versions, or otherwise are working in an environment which gives related errors such as
ERR_REQUIRE_ESM, then please stick with the v26.1.0 release of jsdom. (Noting, of course, that such versions are unsupported, and we will not respond to bug reports opened against them.)Subsequent jsdom releases will explicitly require these minimum Node.js versions, and will have CI testing to ensure that the minimum version is not accidentally raised again.
Normal changelog:
class=""attribute changes is only possible with a new version of jsdom. (@asamuzaK)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.